Auto-redeemable basket level offers in a prepaid architecture

ABSTRACT

A method for maintaining a prepaid payment system comprises a user account that can be utilized to complete a purchase transaction with a merchant. A delayed processing window is introduced between a time when the merchant receives a payment approval notification from the payment system and a time when the payment system transmits a payment request to an issuer of a funding account associated with the user&#39;s payment system account. The payment system utilizes a user&#39;s stored value account maintained by the payment system to satisfy the requirements of a prepaid program, and therefore processes the payment request received from the merchant and transmits the payment approval notification without obtaining prior authorization from the issuer of the funding account. The payment system submits one or more payment requests for the funding transaction at a time after the completion of the purchase transaction between the user and the merchant.

RELATED APPLICATION

This patent application claims priority under 35 U.S.C. §119 to U.S.Patent Application No. 61/826,475, filed May 22, 2013 and entitled“Delayed Processing Window in a Prepaid Architecture.” The entirecontents of the above-identified application are hereby fullyincorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to a payment system, and moreparticularly to methods and systems that allow a delayed processingwindow between a point-of-sale transaction authorization and a paymentauthorization request.

BACKGROUND

In a conventional merchant-consumer financial transaction, the userprovides actual debit or credit card account information to the merchantby way of swiping the actual card, entering the actual card accountnumber, scanning a code comprising the actual card account number, orotherwise transmitting the actual card account number to the merchantsystem. The merchant system's point of sale terminal or online paymentprocess engine submits a payment request to the issuer of the accountthrough the corresponding card network. If funds are available, theissuer sends an authorization code to the merchant system to signalapproval of the payment transaction. The payment process involves asingle payment request generated and submitted by the merchant systemand comprising the user's actual account number. The issuer receives thepayment request from the merchant's system and communicates theauthorization to the merchant's system in real-time.

SUMMARY

In certain example aspects described herein, a method for maintaining aprepaid payment system comprises a payment management system thatmaintains an account for a user, wherein the user can utilize theaccount to complete a purchase transaction with a merchant system. In anexample embodiment, the user can conduct a transaction using one or morefinancial accounts associated with a digital wallet account maintainedby the payment management system in a manner that is compliant withprepaid operating regulations of the financial accounts. In thisembodiment, a delayed processing window is introduced between (1) a timewhen the user completes the transaction with the merchant by presentinga payment management system account identifier (for example, a proxycard, a wireless “tap” of a user device, a bar code, token, or otherform of account identifier) and the merchant system receives a paymentapproval notification from the payment management system, and (2) a timewhen the payment management system transmits a payment request to anissuer of the financial account associated with the payment managementsystem account and receives a payment approval notification from theissuer.

In an example embodiment, the payment management system redeems offersselected by the user and stored in the user's payment management systemaccount. In an example embodiment, the payment management systemutilizes a user's stored value account maintained by the paymentmanagement system to satisfy the requirements of a prepaid programpursuant to any applicable operations, such as the Prepaid OperatingRegulations, and therefore processes the payment request received fromthe merchant system and transmits the payment approval notificationwithout obtaining prior authorization from another issuer of a fundingaccount. In this embodiment, the user may not have a prepaid balance inthe user's stored value account maintained by the payment managementsystem when the payment request transmitted by the merchant system isapproved. The payment management system submits one or more paymentrequests for a funding transaction via the user's one or more registeredpayment accounts at a time after the completion of the purchasetransaction between the user and the merchant system. The paymentmanagement system maintains a dynamic electronic receipt that is updatedwith each action taken by the payment management system in connectionwith the purchase transaction and the funding transaction. In an exampleembodiment, the payment management system can process a returntransaction by identifying the original purchase transaction and fundingthe refund to the financial account that corresponds to the fundingtransaction.

These and other aspects, objects, features, and advantages of theexample embodiments will become apparent to those having ordinary skillin the art upon consideration of the following detailed description ofillustrated example embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a payment system, in accordance withcertain example embodiments.

FIG. 2 is a block diagram depicting a payment flow, in accordance withcertain example embodiments.

FIG. 3 is a block flow diagram depicting a method for processing apurchase transaction utilizing a delayed processing window between apoint-of-sale transaction authorization and a payment authorizationrequest, in accordance with certain example embodiments.

FIG. 4 is a block flow diagram depicting a method for transmitting thepayment authorization request to the payment management system for afronting transaction, in accordance with certain example embodiments.

FIG. 5 is a block flow diagram depicting a method for applying offers,in accordance with certain example embodiments.

FIG. 6 is a block flow diagram depicting a method for identifying amerchant system from the payment authorization request for the frontingtransaction, in accordance with certain example embodiments.

FIG. 7 is a block flow diagram depicting a method for transmitting apayment authorization to the merchant system for the frontingtransaction, in accordance with certain example embodiments.

FIG. 8 is a block flow diagram depicting a method for determining afunding account for a funding transaction, in accordance with certainexample embodiments.

FIG. 9 is a block flow diagram depicting a method for transmitting apayment authorization request for the funding transaction, in accordancewith certain example embodiments.

FIG. 10 is a block flow diagram depicting a method for transmitting apayment declination notification for the funding transaction, inaccordance with certain example embodiments.

FIG. 11 is a block flow diagram depicting a method for transmitting apayment authorization notification for the funding transaction, inaccordance with certain example embodiments.

FIG. 12 is a block flow diagram depicting a method for processing areturn transaction in the payment system, in accordance with certainexample embodiments.

FIG. 13 is a block flow diagram depicting a method for transmitting arefund notification to the payment management system, in accordance withcertain example embodiments.

FIG. 14 is a block flow diagram depicting a method for identifying apayment account for the funding transaction that corresponds to thereturn transaction, in accordance with certain example embodiments.

FIG. 15 is a block flow diagram depicting a method for transmitting arefund notification to an issuer of the payment account for the fundingtransaction that corresponds to the return transaction, in accordancewith certain example embodiments.

FIG. 16 is a block diagram depicting a computer machine and module, inaccordance with certain example embodiments.

FIG. 17 a is a block diagram depicting a dynamic electronic receiptcomprising information received from a payment request, in accordancewith certain example embodiments.

FIG. 17 b is a block diagram depicting an updated dynamic electronicreceipt comprising information on an offer redeemed, in accordance withcertain example embodiments.

FIG. 18 is a block diagram depicting an updated dynamic electronicreceipt comprising information on an updated purchase request amount, inaccordance with certain example embodiments.

FIG. 19 is a block diagram depicting an updated dynamic electronicreceipt comprising information on a payment from a stored value accountand an adjusted transaction amount, in accordance with certain exampleembodiments.

FIG. 20 is a block diagram depicting an updated dynamic electronicreceipt comprising information on payment requests submitted, inaccordance with certain example embodiments.

FIG. 21 is a block diagram depicting an updated dynamic electronicreceipt comprising information on a declination notice received, inaccordance with certain example embodiments.

FIG. 22 is a block diagram depicting an updated dynamic electronicreceipt comprising information on payment authorizations, in accordancewith certain example embodiments.

FIG. 23 is a block diagram depicting an updated dynamic electronicreceipt comprising information on refund requests, in accordance withcertain example embodiments.

DETAILED DESCRIPTION OF THE EXAMPLE EMBODIMENTS

Proxy account payment systems enable users to utilize a single financialaccount to associate and access multiple financial accounts maintainedby multiple issuers. The user receives a proxy account from a paymentmanagement system and either creates a new payment system account orassociates the proxy account with the user's digital wallet accountalready maintained by the payment management system. The user thenassociates one or more financial card accounts with the proxy account.For example, the user can associate with the user's proxy card accountmultiple debit/credit cards maintained by multiple issuers (includingthe payment system operating as an issuer), stored value cards (forexample, gift accounts, prepaid accounts, re-loadable transactionaccounts, exchange accounts, and other forms of non-credit based valueaccounts), loyalty accounts or store rewards accounts, value addedservice accounts (for example, coupons, vouchers for prepaid offers,redemption offers, and other forms of offers), and/or other forms offinancial card accounts.

The user applies the proxy account to a transaction with the merchant ina manner similar to the application of any other financial account to atransaction. The merchant forwards the payment request to an acquirer,which forwards the payment request to the payment management system(which functions as the issuer for the payment request) via a cardnetwork. The payment management system can read proxy accountinformation from the payment request and can access the user's accountassociated with the proxy account. If the payment management system isthe issuer of a financial account selected as the funding account, thepayment system will approve or decline the transaction. If anotherissuer maintains the funding account, the payment management system willgenerate and send a new payment request to the issuer via the cardnetwork. The payment management system will receive the authorizationmessage from the issuer via the card network if the transaction isapproved. The payment management system forwards an authorization to theacquirer through the card network, which forwards the authorization tothe merchant. The merchant then approves the transaction.

In the proxy account payment system, the transaction between themerchant and the user is approved after the payment management systemreceives approval from the issuer of the funding account indicating thatthe funding account has a sufficient available balance to process thetransaction. The payment management system sends the payment request tothe issuer in real-time with the transaction to obtain approval and totransmit the authorization to the merchant.

Example System Architectures

Turning now to the drawings, in which like numerals indicate like (butnot necessarily identical) elements throughout the figures, exampleembodiments are described in detail.

FIG. 1 is a block diagram depicting a payment system, in accordance withcertain example embodiments. As depicted in FIG. 1, the exemplaryoperating environment 100 comprises a user account device 105, amerchant system 110, a user device 120, a payment management system 130,an acquirer system 150, and an issuer system 160 that are configured tocommunicate with one another via one or more networks 140. In analternative example embodiment, two or more of these systems (includingsystems 110, 120, 130, 150, and 160) are integrated into the samesystem.

Each network 140 includes a wired or wireless telecommunication means bywhich network systems (including systems 110, 120, 130, 150, and 160)can communicate and exchange data. For example, each network 140 can beimplemented as, or may be a part of, a storage area network (SAN),personal area network (PAN), a metropolitan area network (MAN), a localarea network (LAN), a wide area network (WAN), a wireless local areanetwork (WLAN), a virtual private network (VPN), an intranet, anInternet, a mobile telephone network, a card network, Bluetooth, nearfield communication network (NFC), any form of standardized radiofrequency, or any combination thereof, or any other appropriatearchitecture or system that facilitates the communication of signals,data, and/or messages (generally referred to as data). Throughout thisspecification, it should be understood that the terms “data” and“information” are used interchangeably herein to refer to text, images,audio, video, or any other form of information that can exist in acomputer-based environment.

In an example embodiment, each network system (including systems 110,120, 130, 150, and 160) includes a device having a communication modulecapable of transmitting and receiving data over the network 140. Forexample, each network system (including systems 110, 120, 130, 150, and160) may comprise a server, personal computer, mobile device (forexample, notebook computer, tablet computer, netbook computer, personaldigital assistant (PDA), video game device, GPS locator device, cellulartelephone, Smartphone, or other mobile device), a television with one ormore processors embedded therein and/or coupled thereto, point of saledevice, or other appropriate technology that includes or is coupled to aweb browser or other application for communicating via the network 140.In the example embodiment depicted in FIG. 1, the network systems(including systems 110, 120, 130, 150, and 160) are operated bymerchants, users 101, a payment management system operator, acquirersystem operator, and issuer system operator, respectively.

The merchant system 110 comprises at least one point of sale (POS)terminal 115 that is capable of processing a purchase transactioninitiated by a user 101. In an example embodiment, the merchant operatesan online store and the user 101 indicates a desire to make a purchaseby clicking a link or “checkout” button on a website. In another exampleembodiment, the user device 120 is configured to perform the functionsof the POS terminal 115. In this example, the user 101 scans and/or paysfor the transaction via the user device 120 without interacting with thePOS terminal 115.

In an example embodiment, the merchant system 110 is capable ofcommunicating with the user device 120 via an application (not shown).The application (not shown) may be an integrated part of the POSterminal 115 or a standalone hardware device (not shown), in accordancewith another example embodiment.

In an example embodiment, the user device 120 may be a personalcomputer, mobile device (for example, notebook, computer, tabletcomputer, netbook computer, personal digital assistant (PDA), video gamedevice, GPS locator device, cellular telephone, Smartphone or othermobile device), television, or other appropriate technology thatincludes or is coupled to a web server, or other suitable applicationfor interacting with web page files. The user 101 can use the userdevice 120 to access a payment management system 130 user account via auser interface 121 and an application 123. The application 123 is aprogram, function, routine, applet or similar entity that exists on andperforms its operations on the user device 120. For example, theapplication 132 may be one or more of a shopping application, merchantsystem 110 application, an Internet browser, a digital walletapplication, a loyalty card application, another value-addedapplication, a user interface 121 application, or other suitableapplication operating on the user device 120. In some embodiments, theuser 101 must install an application 123 and/or make a feature selectionon the user device 120, as part of a user account, etc., to obtain thebenefits of the techniques described herein.

An example user device 120 comprises a secure element 127 or securememory, which can exist within a removable smart chip or a securedigital (SD) card or which can be embedded within a fixed chip on thedevice 120. In certain example embodiments, Subscriber Identity Module(SIM) cards may be capable of hosting a secure element 127, for example,an NFC SIM Card. The secure element 127 allows an application 123resident on the device 120 and accessible by the device user 101 tointeract securely with certain functions within the secure element 127,while protecting information stored within the secure element 127. Thesecure element 127 comprises applications running thereon that performthe functionality described herein. In an example embodiment, the secureelement 127 comprises components typical of a smart card, such as cryptoprocessors and random generators. In an example embodiment, the secureelement 127 comprises a Smart MX type NFC controller in a highly securesystem on a chip controlled by a smart card operating system, such as aJavaCard Open Platform (JCOP) operating system. In another exampleembodiment, the secure element 127 is configured to include a non-EMVtype contactless smart card, as an optional implementation. The secureelement 127 communicates with the application 123 in the user device120. In an example embodiment, the secure element 127 is capable ofstoring encrypted user information and only allowing trustedapplications to access the stored information. In an example embodiment,a controller 125 interacts with a secure key encrypted application 123for decryption and installation in the secure element 127.

Additionally, the secure element 127 also may comprise secure softwareapplications, such as payment applications, secure forms of theapplications, authentication applications, payment provisioningapplications, or other suitable application using the securefunctionality of the secure element 127.

In an example embodiment, the data storage unit 129 and application 123may be implemented in the secure element 127, as described previously,on the user device 120. In another example embodiment, the data storageunit 129, may be a separate memory unit resident on the user device 120.An example data storage unit 129 enables storage of user contact detailsfor retrieval of a payment management system 130 account. In an exampleembodiment, the data storage unit 129 can include any local or remotedata storage structure accessible to the user device 120 suitable forstoring information. In an example embodiment, the data storage unit 129stores encrypted information, such as HTML5 local storage.

The user device 120 also comprises a controller 125. In an exampleembodiment, the controller 125 is an NFC controller. In some exampleembodiments, the controller 125 is a Bluetooth link controller. TheBluetooth link controller may be capable of sending and receiving data,performing authentication and ciphering functions, and directing how theuser device 120 will listen for transmissions from the POS terminal 115or configure the user device 120 into various power-save modes accordingto the Bluetooth-specified procedures. In another example embodiment,the controller 125 is a Wi-Fi controller or an NFC controller capable ofperforming similar functions.

In an example embodiment, the POS terminal 115 is capable ofcommunicating with the user device 120 using an NFC communicationmethod. In another example embodiment, the POS terminal 115 is capableof communicating with the user device 120 using a Bluetoothcommunication method. In yet another example embodiment, the POSterminal 115 is capable of communicating with the user device 120 usinga Wi-Fi communication method. In some example embodiments, the user 101scans a QR code or bar code or clicks a URL link on the user device 120,which temporarily associates the user device 120 to an online merchantsystem 110. The POS terminal 115 queries the online merchant system 110to link to the user device 120.

The user device 120 communicates with the POS terminal 115 via anantenna 126. In an example embodiment, once a user device application123 has been activated and prioritized, the controller 125 is notifiedof the state of readiness of the user device 120 for a transaction. Thecontroller 125 outputs through the antenna 126 a radio signal, orlistens for radio signals from the POS terminal 115. On establishing acommunication channel between the user device 120 and the POS terminal115, the POS terminal 115 requests a payment processing response fromthe user device 120.

An example controller 125 receives a radio wave communication signalfrom the POS terminal 115 transmitted through the antenna 126. Thecontroller 125 converts the signal to readable bytes. In an exampleembodiment, the bytes comprise digital information, such as a requestfor a payment processing response or a request for payment cardinformation. The controller 125 transmits the request to the secureelement 127.

In another example embodiment, the user 101 communicates with POSterminal 115 via the user account device 105. In an example embodiment,the user account device 105 looks and/or functions in the same manner asa standard credit or debit card. For example, the user account device105 may have the user's name and/or account number listed on the frontof the card. An exemplary user account device 105 can include a magneticstripe encoding the user's payment management system 130 accountinformation. In an example embodiment, the account information encodedin the magnetic stripe routes payment requests to the payment managementsystem 130 for processing.

In yet another example embodiment, the user account device 105 is anaccount identification number, a bar code or QR code, a token, or otherform of account identification or access, which may be entered manuallyinto the POS terminal 115 or which may be captured by the POS terminal115. The user account device 105 as discussed throughout thespecification refers to a physical card as well as the other forms ofaccount identification or access.

An example user device 120 communicates with the payment managementsystem 130. The payment management system 130 comprises a user accountmodule 131, offers module 133, risk analysis module 135, a data storageunit 137, a payment module 138, and a returns module 139. In an exampleembodiment, the user 101 creates an account with the payment managementsystem 130. The user account module 131 manages the registration of theuser 101. Regarding user account registration, the user account module131 may generate web-based user interfaces providing forms for the user101 to register for a payment management system 130 account. Forexample, the user account module 131 can collect basic user identifyinginformation, registration information on one or more user devices 120,and payment information. In an example embodiment, the user 101registers one or more financial accounts, including bank account debitcards, credit cards, stored value accounts, gift cards, a link to aproxy for one or more financial accounts (for example, a digital walletlink where the digital wallet is connected to other payment accounts),or other type of financial account that can be used to make a purchase,with the payment management system 130 using the user account module131. In an example embodiment, the registered financial paymentinformation may be used to complete a purchase by the user 101 with themerchant system 110. In an example embodiment, the user accountinformation is stored in a user account or is otherwise associated inthe data storage unit 137 with the user 101. The user may access thedigital wallet account at any time to add, change or remove paymentaccounts. In an example embodiment, the payment management system 130transmits limited-use proxy account information to the user device 120enabling use of the payment accounts during a payment transaction routedto the payment management system 130 during the payment processing. Forexample, the proxy account number route the payment authorizationrequest to the payment management system 130, acting as the issuersystem 170 for the proxy account. In another example embodiment, theapplication 123 on the user device 120 may generate limited use proxyaccount numbers that enable the payment transaction to be routed to thepayment management system 130.

An example offers module 133 receives offers from the merchant system110 and distributes the offers to users 101 for review and selection. Inanother example embodiment, the offer module 133 may generate web-baseduser interfaces providing forms for the merchant system 110 to createoffers. The offers may be prepaid offers, wherein the user 101 pays aspecified amount for the offer prior to redeeming the offer with themerchant system 110. The user 101 selects the offer distributed by theoffer module 133. In an example embodiment, the user 101 selects anoffer by clicking on it and saving it in the user's digital walletapplication 123, which may then be uploaded to the payment managementsystem 130 and associated with the user's 101 account.

In an example embodiment, the data storage unit 137 can include anylocal or remote data storage structure accessible to the paymentmanagement system 130 suitable for storing information. In an exampleembodiment, the data storage unit 137 stores encrypted information, suchas HTML5 local storage.

In an example embodiment, the user device 120 and/or user account device105 communicate payment information to the merchant system 110 in theform of a proxy or virtual account identifier, without transmitting theuser's actual account information. The user's actual account informationis maintained by the payment management system 130. The merchant system110 receives the user's 101 payment information and interacts with theacquirer system 150 (for example third party payment processingcompanies) to process a payment request. The user's 101 paymentinformation routes the merchant system's 110 payment request to thepayment management system 130. The payment management system 130receives the payment request and the offers module 133 determineswhether the user 101 has an offer applicable to the transaction. In anexample embodiment, any offers applicable to the transaction are appliedthereby reducing the transaction amount.

In an example embodiment, the risk analysis module 135 determineswhether to authorize the transaction. In an example embodiment, the riskanalysis module 135 performs the risk analysis and, if there isappropriately-low risk, authorizes the merchant system 110 paymentrequest without seeking prior authorization for a payment account savedin the user's 101 payment management system 130 account. For example,the payment request is authorized based on information contained in theuser's 101 payment management system 130 account and not based onreceiving a payment authorization received by the issuer system 160corresponding to the payment account.

The payment management system 130 transmits a payment authorizationnotification to the merchant system 110 through the acquirer system 150.The payment management system 130 then transmits the issuer system 170(for example Bank X and other financial institutions to authorizepayment) to process the payment.

In an example embodiment, the payment module 138 then determines whichfinancial account to charge or deduct the transaction balance to. In anexample embodiment, the user 101 has defined rules for determining whichpayment account the payment management system 130 will submit thepayment request to. In an example embodiment, the user 101 has a prepaidbalance in a digital wallet account maintained by the payment managementsystem 130. In this embodiment, the payment management system 130 willdeduct a portion of or the entire amount of the transaction from theprepaid balance. In an example embodiment, maintaining a sufficientprepaid balance to cover part of or all of the purchase transaction maybe evaluated by the risk analysis module 135 when determining whether toauthorize the purchase transaction.

In another example embodiment, the payment module 138 submits a paymentrequest to the issuer system 160 that corresponds to the user's 101payment account information selected to charge the transaction balanceto. In yet another example embodiment, the payment module 138 may chargethe transaction balance to multiple different payment accounts. In anexample embodiment, the payment module 138 will receive notification ofan approved payment transaction from the issuer system 160. In anotherexample embodiment, the payment module 138 will receive notification ofa declined payment transaction from the issuer system 160. In thisembodiment, the payment management system 130 will log the declinedtransaction and the payment module 138 will submit a new payment requestto the issuer system 160 for a different payment account.

In an example embodiment, the payment management system 130 logs eachpayment request, payment declination, and payment authorization in adynamic transaction receipt. In an example embodiment, a receiptcomprises a written record for the transaction that is presentedelectronically. In an example embodiment, the receipt is available forreview by the user 101 in the user's payment management system 130account.

In an example embodiment, the user 101 processes a return with themerchant system 110. In this embodiment, the return if transmitted tothe payment management system 130 in a manner consistent with that of apayment request. The returns module 139 reviews the informationcontained in the refund request and authorizes a credit to the user's101 corresponding payment account. In an example embodiment, the returnsmodule 139 uses logic to determine the corresponding payment transactionand the corresponding payment account to credit the return transactionamount to. In an example embodiment, the dynamic transaction receipt isupdated to include the return transaction.

FIG. 2 is a block diagram depicting an example payment flow, inaccordance with certain example embodiments. As depicted in FIG. 2, theexample operating environment 200 comprises a fronting transaction and afunding transaction. In an example fronting transaction, once the user101 initiates the purchase transaction (X) with the merchant system 110,the merchant system submits the payment request (A) and the paymentmanagement system 130 responds with the payment authorization (B). In anexample embodiment, the fronting transaction is completed before thefunding transaction is initiated. In an example funding transaction, thepayment management system 130 initiates the payment request (C) and theissuer system 160 responds with the payment authorization (D). Asdepicted in FIG. 2, the user 101 settles any amount owed to the issuersystem 160 in a separate payment transaction (Z) and the merchant system110 receives the payment remittance (E) from the funding transaction.

The components of the example operating environments 100 and 200 aredescribed hereinafter with reference to the example methods illustratedin FIGS. 3-15. The example methods of FIGS. 3-15 may also be performedwith other systems and in other environments.

Example System Processes

FIG. 3 is a block flow diagram depicting a method for processing apurchase transaction utilizing a delayed processing window between apoint-of-sale transaction authorization and a payment authorizationrequest, in accordance with certain example embodiments. The method 300is described with reference to the components illustrated in FIGS. 1 and2.

In an example embodiment, a payment management system 130 maintains anelectronic account, such as a digital wallet account for a user 101. Inan example embodiment, the user 101 accesses the payment managementsystem 130 via a website and a network 140. In an example embodiment,the user 101 submits registration information to the payment managementsystem 130, including, but not limited to, name, address, phone number,e-mail address, and information for one or more registered financialaccounts, including bank account, debit cards, credit cards, a loyaltyrewards account card, or other type of account that can be used to makea purchase (for example, card type, card number, expiration date,security code, and billing address). In an example embodiment, theuser's 101 payment management system 130 account information is saved inthe data storage unit 137 and is accessible to the user account module131. In an example embodiment, the payment management system 130 accountis a digital wallet account maintained by the payment management system130 or a third party system. In another example embodiment, the user 101may use a smart phone application 123 to register with the paymentmanagement system 130. In yet another example embodiment, the user 101accesses the payment management system 130 via a user device application123.

In an example embodiment, the user 101 is provided with an accountidentifier (for example, an account number, proxy account number, orother form of account identifier) and/or a user account device 105 (forexample, a magnetic stripe card, a bar code, a QR code, or other devicethat may be used to complete a payment transaction with a merchantsystem 110) that corresponds to the user's 101 payment management system130 account.

In block 310, the user 101 initiates a transaction with a merchant. Inan example embodiment, the user 101 browses the merchant system 110online marketplace. In this embodiment, the merchant system 110 onlinemarketplace is an online shopping website wherein the user 101 canselect and purchase items from the merchant system 110. The user 101indicates a desire to place the item in an electronic shopping basket.In an alternative example embodiment, the user 101 has previouslyselected one or more items to be placed in the electronic shoppingbasket and has selected an additional item to be placed in theelectronic shopping basket. In another alternative example embodiment,the user 101 has previously selected one or more items to be placed inthe electronic shopping basket and has indicated a desire to completethe purchase by clicking a “checkout” button in the electronic shoppingbasket. In an example embodiment, the user 101 enters the accountidentifier upon checkout. In this embodiment, the user 101 enters thepayment management system 130 account information in the credit cardfields on the checkout page.

In another example embodiment, the merchant system online marketplaceprovides a link, button, or other control that allows the user 101 toautomatically transmit the user's payment management system 130 accountinformation to the merchant system 110 (for example, a “pay with digitalwallet account” button). In this embodiment, the user 101 is prompted tolog into, has previously logged, or is otherwise automatically loggedinto the payment management system 130. In another example embodiment,the user's 101 login credentials are shared across other accounts (forexample, social networking websites and user device 120 accounts) andthe user 101 is automatically logged into the payment management system140 account using the shared login credentials.

In another example embodiment, the digital wallet application 123 caninteract with the merchant system 110. The merchant's website can detectwhether the user device 120 includes a digital wallet application 123and attach to user's digital wallet. Once attached, the merchant system110 can send a purchase request message to the digital walletapplication 123 requesting payment information. In response to receivinga purchase request message from the merchant system 110, the digitalwallet application 123 can present the user 101 with a user interface121 for the user 101 to confirm the purchase the digital walletapplication 123.

In another example embodiment, the user 101 enters a store of themerchant, selects an item for purchase, and takes the item to a point ofsale device (for example, a POS terminal 115) of the merchant system 110to purchase the item. In this embodiment, the user 101 may use the useraccount device 105 in a manner consistent with a magnetic stripe creditcard. In another embodiment, a payment code is displayed on the userinterface 121 of the user device 120 in a manner that the merchantsystem 110 and/or user 101 can read the code. In an example embodiment,the payment code is a bar code, QR code, or other machine-readable codethat is capable of being scanned by a code scanner or otherwise readableby the merchant system 110. In another example embodiment, the paymentcode is displayed on the user interface 121 so that a merchant operatingthe merchant system 110 can read and physically enter the payment codeinto the POS terminal 115. In an alternative example embodiment, thepayment code is read by the user 101 and entered into the POS terminal115.

In another example embodiment, the user 101 using the user device 120 toinitiate a contactless “tap” with the POS terminal 115. In operation ofan NFC, Bluetooth, Wi-Fi, or other wireless transaction, the user 101“taps” the user device 120, such as an NFC-enabled user device 120, toPOS terminal 115 of a point of sale system. The POS terminal 115recognizes the NFC-enabled device 120 when the device is moved withinrange of the POS terminal 115, establishes a secure communicationchannel with the device 120, and initiates a payment transaction betweenthe POS terminal 115 and the device 120.

In block 320, the merchant system 110 transmits a payment request forthe purchase transaction to the account management system 130. In anexample embodiment, the submission of the payment request by themerchant system for the purchase transaction signifies the beginning ofthe fronting transaction as illustrated on FIG. 2. The payment requestfunctions to seek approval for the purchase transaction via the accountinformation provided by the user 101. In an example embodiment, themerchant system 110 processes the purchase transaction in a mannerconsistent with a typical debit card or credit card transaction. Themethod for transmitting the payment authorization request to the paymentmanagement system 130 for the fronting transaction is described in moredetail hereinafter with reference to the methods described in FIG. 4.

FIG. 4 is a block flow diagram depicting a method 320 for transmittingthe payment authorization request to the payment management system 130for the fronting transaction, in accordance with certain exampleembodiments, as referenced in block 320. The method 320 is describedwith reference to the components illustrated in FIGS. 1 and 2.

In block 410, the merchant system 110 generates a payment requestmessage to request payment using the account information provided by theuser 101 in block 310 and transmits the payment request to an acquirersystem 150. In an example embodiment, the account information resemblesactual debit/credit card information and the POS terminal 115 processesthe transaction in a manner consistent with a typical payment request.

In block 420, the acquirer system 150 receives the payment request. Inan example embodiment, the acquirer system 150 receives the paymentrequest in a manner consistent with a typical debit card or credit cardtransaction.

In block 430, the acquirer system 150 transmits the payment request to acard network 140. In an example embodiment, the acquirer system 150transmits the payment request in a manner consistent with a typicaldebit card or credit card transaction. In an example embodiment, theaccount information provided by the user 101 in block 310 can be readand understood by the acquirer system 150, which allows the acquirersystem 150 to transmit the request to the appropriate card network 140.

In block 440, the card network receives the payment request. In anexample embodiment, the card network receives the payment request in amanner consistent with a typical debit card or credit card transaction.

In block 450, the card network 140 transmits the payment request to thepayment management system 130. In an example embodiment, the accountinformation provided by the user 101 in block 310 can be read andunderstood by the card network 140, which allows the card network 140 totransmit the request to the payment management system 130. In thisembodiment, the card network 140 reads an account number from theaccount information and determines, based on a series of numbers orrouting information contained in the account number, that the paymentrequest should be transmitted to the payment management system 130.

In block 460, the payment management system 130 receives the paymentrequest.

The method 320 then proceeds to block 330 in FIG. 3.

Returning to FIG. 3, in block 330, the payment management system 130identifies the user 101 account associated with the payment requestreceived from the merchant system 110. In an example embodiment, thepayment management system 130 uses the information contained in thepayment request to identify the user's 101 account. In an exampleembodiment, the payment management system 130 reads the user's 101account identification information from the payment request. In anexample embodiment, the user's 101 identification information iscontained in or encoded by the account information. In another exampleembodiment, the payment management system 130 cross-references a list ofgenerated account numbers to determine the corresponding user 101account.

In another example embodiment, the user 101 is conducting an onlinetransaction with the merchant system 110 or a transaction via a merchantshopping application 123 resident on the user device 120 and the user101 is logged into the user's payment management system 130 account.

In block 340, the payment management system 130 applies any offersavailable for the purchase transaction. The method for applying offersis described in more detail hereinafter with reference to the methodsdescribed in FIG. 5.

FIG. 5 is a block flow diagram depicting a method 340 for applyingoffers, in accordance with certain example embodiments, as referenced inblock 340. The method 340 is described with reference to the componentsillustrated in FIGS. 1 and 2.

In an example embodiment, the payment management system 130 distributesoffers online. In an example embodiment, the merchant system 110registers with the payment management system 130 and transmits an offerto the payment management system 130 for online distribution. In anexample embodiment, the offers may include, but are not limited to,coupons, loyalty points, prepaid offers, rebates, and other forms ofvalue added services. In another example embodiment, the offers areprovided by a manufacturer system (not shown) or another third partysystem.

In an example embodiment, the offers are for a specific product or groupof products. For example, the offer may be for $1.00 off Brand A laundrydetergent or $1.00 off a Brand B product. These offers may be redeemedat any merchant that accepts manufacturer coupons. In another exampleembodiment, the offers are for a particular merchant. For example, theoffer may be for $10 off a $50 purchase at Merchant X. In an alternativeexample embodiment, the offers comprise loyalty reward pointredemptions. For example, the offer may be for 10 loyalty points forevery purchase of a Manufacturer B product.

In an example embodiment, the offers comprise details on how the offercan be redeemed and redemption rules. For example, the offer maycomprise the identification of the item to be purchased, such as producttitle, brand information, universal product code (UPC), a stock keepingunit (SKU), a Japanese article number (JAN), a world product code (WPC),International Standard Book Number (ISBN), European Article Number(EAN), color, size, and other relevant sale information.

In an example embodiment, the merchant system 110 creates the offeroutside of the payment management system 130. In an alternative exampleembodiment, the payment management system 130 may generate web-baseduser interfaces providing forms for the merchant system 110 to createoffers.

In an example embodiment, the user device 120 displays the offer for theuser 101 to review. In an example embodiment, the offer is displayed inan offer application 123 resident on the user device 120. In anotherexample embodiment, the offer is displayed in response to an Internetsearch, in an electronic message or text message, or as a banner in anInternet browser. In an example embodiment, the user 101 selects theoffer and saves it to the user's payment management system 130 account.

In block 510, the payment management system 130 creates a dynamicelectronic receipt comprising the information received from the paymentrequest. In an example embodiment, the dynamic electronic receipt is awritten record for the transaction that is presented electronically. Inan example embodiment, the dynamic electronic receipt comprises alisting of each action taken by the payment management system 130 withrespect to the purchase transaction (including the fronting transactionand the funding transaction). In an example embodiment, the dynamicelectronic receipt is saved in the data storage unit 137 and isavailable for review by the user 101 in the user's payment managementsystem 130 account. FIG. 17 a illustrates an example dynamic electronicreceipt 3010. In this example, Merchant A transmitted a payment requestfor $100 to the payment management system 130 for a purchase transactionbetween Merchant A and User X.

Returning to FIG. 5, in block 520, the payment management system 130identifies the merchant system 110 based on the information contained inthe payment request. In an example embodiment, the payment managementsystem 130 maintains a database of known merchant systems 110 and thecorresponding merchant identification (ID) codes or merchant descriptioninformation (for example, merchant name, address, phone number,franchise name or location, franchisee/owner name, franchisee/branchnumber, and other identifying information). The method for identifyingthe merchant system 110 from the payment authorization request for thefronting transaction is described in more detail hereinafter withreference to the methods described in FIG. 6 a.

FIG. 6 a is a block flow diagram depicting a method 520 for identifyingthe merchant system 110 from the payment authorization request for thefronting transaction, in accordance with certain example embodiments, asreferenced in block 520. The method 520 is described with reference tothe components illustrated in FIGS. 1 and 2.

In block 610, the payment management system 130 reads the paymentrequest. In an example embodiment, the information required to identifythe merchant system 110 can be obtained from the payment request andcross-referenced to the database of known merchant systems 110.

In block 620, the payment management system 130 determines whether themerchant ID code is available on the payment request. In an exampleembodiment, the payment management system 130 reads the merchant ID codefrom the payment request and cross-references the code to the merchantID codes of known merchant systems to identify the merchant system 110.

In an example embodiment, the merchant system 110 has previouslyprovided the payment management system 130 with a merchant'sidentification (ID) (for example, when registering with the paymentmanagement system 130, when providing the payment management system 130offers for distribution, or when otherwise conducting business with thepayment management system 130).

If the merchant ID code is available, the method 520 proceeds to block630. In block 630, the payment management system 130 compares themerchant ID code provided in the payment request to the merchant ID codeprovided in the offers saved in the user's 101 payment management system130 account. In an example embodiment, the merchant system 110 createdthe offers for distribution by the payment management system 130 andprovided the merchant ID codes for inclusion on the offers when theywere created.

From block 630 in FIG. 6, the method 520 proceeds to block 530 in FIG.5.

Returning to block 620, if the payment request does not contain themerchant ID, the method 520 proceeds to block 640.

In block 640, the payment management system 130 reads a merchantdescriptor from the payment request. In an example embodiment, thepayment request comprises a descriptor that identifies the merchantsystem 110, for example, a name, address, location, phone number,franchisee name/location, owner name, or other descriptor thatidentifies the merchant system 110. In an example embodiment, thedescriptor can comprise an identification of a branch, franchise, ordivision of a merchant system (for example, a fast food restaurantfranchise located on street X in town Z).

In block 650, the payment management system 130 identifies the merchantsystem 110 based on the merchant descriptor read from the paymentrequest in block 640. In an example embodiment, the payment managementsystem 130 compares the merchant descriptor (for example, an address,name, phone number, franchise name, franchise location, franchisee nameor owner name, and franchisee or branch number) to a known merchantsystem. In an example embodiment, the payment management system 130matches the merchant descriptor to a known merchant identifier. Inanother example embodiment, the payment management system 130 uses amerchant type identifier (for example, a merchant category code or MCC)to aid in the identification of the merchant system 110. For example,the payment management system 130 can distinguish between differentmerchant systems 110 with similar names using the MCC. In yet anotherexample, the payment management system 130 uses the acquirer system 150name to aid in the identification of the merchant system 110. Forexample, the all Merchant X stores use Acquirer B as the acquirer system150.

In block 660, the payment management system 130 compares the merchantdescriptor and/or merchant system 110 identified in block 650 to themerchant ID code and/or merchant descriptor provided in the offers. Inan example embodiment, payment management system 130 cross-referencesthe merchant system 110 information and the offers saved in the user's101 payment management system 130 account.

The method 520 then proceeds to block 530 in FIG. 5.

Returning FIG. 5, in block 530, the payment management system 130determines whether the user 101 has offers available to the purchasetransaction. In an example embodiment, one or more of the offers areapplicable to a transaction with a specific merchant system 110. In analternative example embodiment, the offer is provided by the paymentmanagement system 130 and is applicable to a transaction with anymerchant system 110.

If no offers are available, the method 340 proceeds to block 350 in FIG.3.

Returning to block 530 in FIG. 5, if offers are available, the method340 proceeds to block 540 in FIG. 5.

In block 540, the payment management system 130 reviews the redemptionrules for the offer. In an example embodiment, each offer will have oneor more rules or conditions associated with it that the paymentmanagement system 130 can understand without human intervention. Theserule include, but are not limited to a purchase threshold (for example,receive $1.00 off Brand Z laundry detergent that is regularly priced$5.00 or more, or $10 single purchase of more than $50 from Merchant X),an aggregate purchase threshold (for example, receive $10 off nextpurchase from a merchant after the accumulated purchase of ManufacturerB products has reached $100), a minimum number of purchases of an item(for example, receive $10 off your tenth purchase of Brand Z items), atime restriction (for example, receive $10 off a lunch-time purchase), amaximum discount (for example, the merchant system 110 sets $10 off as amaximum and user A gets $1 off, while user B gets $2 off), and/or alocation restriction (for example, receive $10 off a purchase at aspecified location). In an example embodiment, these rules are set bythe merchant system 110 at the time the offer is created and reviewedbefore the offer is applied. In an alternative example embodiment, theoffer is a prepaid offer and the redemption rules may include anexpiration date. The offer content and discount may be personalized to aparticular user. For example, user A may receive a 5% off coupon for aparticular product or service while user B may receive a 10% off couponfor the same product or service. The payment management system 130 maydistribute the offers and selectively send potential offers to the user101. The payment management system 130 may determine which users qualifyfor a particular offer. The payment management system 130 may also rankand prioritize the offers sent to a user 101.

In block 550, the payment management system 130 determines whether theredemption rules are satisfied by the purchase transaction. In anexample embodiment, the payment management system 130 reviews the termsof the offer and the payment request to determine which of the offersare applicable to the purchase transaction.

If no offers are applicable to the purchase transaction, the method 340proceeds to block 350 in FIG. 3.

Returning to block 550 in FIG. 5, if offers are applicable to thepurchase transaction, the method 340 proceeds to block 560. In anexample embodiment, more than one offer may be applied to the purchasetransaction. In another example embodiment, only one offer may beapplied to the purchase transaction. In this embodiment, the paymentmanagement system 130 may determine which offer provides the user 101with the greatest savings.

In block 560, the payment management system 130 marks the offer asredeemed. In an example embodiment, after the offer is marked asredeemed it is not available for redemption during a different paymenttransaction.

In block 570, the payment management system 10 updates the dynamicelectronic receipt to reflect the redemption of the offer. In an exampleembodiment, the user 101 is notified of the redemption of the offer inreal-time (for example, notification is transmitted via electronic mail,SMS, or other form of communication). In an example embodiment, the user101 is provided with a copy of the dynamic electronic receipt (forexample, a copy is sent via electronic mail, a link to the dynamicelectronic receipt is provided, a notification is transmitted indicatingthat the dynamic electric receipt was updated, or other form ofnotification is provided). Continuing with the previous exampleillustrated in FIG. 17 b, an offer for $10 off a purchase with MerchantA was applied to the transaction between User X and Merchant A and thedynamic electronic receipt 3010 was updated to reflect the redemption ofthe offer.

Returning to FIG. 5, in block 580, the payment management system 130deducts the amount of the offer from the payment request amount. In anexample embodiment, the payment management system 130 calculates anadjusted transaction amount after each offer is applied.

In block 590, the payment management system updates the dynamicelectronic receipt to reflect the adjusted transaction amount.Continuing with the previous example illustrated in FIG. 18, the paymentmanagement system 130 deducted the $10 value of the offer from the $100purchase request amount to calculate the $90 adjusted request amount andthe dynamic electronic receipt 3010 was updated to reflect the adjustedtransaction amount.

Returning to FIG. 5, the method 340 continues to block 345 in FIG. 3.

Returning to FIG. 3, in block 343, the payment management system 130determines whether the user 101 has a stored value account balance. Inan example embodiment, the user's 101 stored value account is a prepaidaccount maintained by the payment management system 130, as describedwith reference to block 350 in FIG. 3.

If the user 101 does not a have a stored value account balance, themethod 300 proceeds to block 350 in FIG. 3.

Returning to block 343, if the user 101 has a stored value accountbalance, the method 300 proceeds to block 345.

In block 345, the payment management system 130 deducts the adjustedpayment request amount from the stored value account balance. In anexample embodiment, the payment management system 130 is the issuersystem 160 for the stored value account. In another example embodiment,the stored value account is maintained by a third party issuer system160 and the payment management system 130 deducts the balance from thestored value account by submitting a payment request as described hereinwith reference to block 380 in FIG. 3.

In block 347, the payment management system updated the dynamicelectronic receipt to reflect payment for the funding transaction viathe stored value account. Continuing with the previous example asillustrated in FIG. 19, $50 of the transaction balance ($90) wasdeducted from the stored value account and the dynamic electronicreceipt 3010 was updated to reflect the payment from the stored valueaccount.

Returning to FIG. 3, in block 350, the payment management system 130determines whether to approve the payment request. In an exampleembodiment, the payment management system 130 executes an algorithm, alogic program, or otherwise determines whether to approve the paymentrequest without receiving notification of an approved fundingtransaction. For example, the payment management system 130 may evaluatefactors (such as whether the user 101 has a positive stored valueaccount balance) to determine whether to approve the payment requestwithout obtaining prior approval for the funding transaction from anissuer system 160 corresponding to a funding account designated by theuser 101.

In an example embodiment, the user 101 is prompted to establish a storedvalue account when creating and/or updating the user's 101 paymentmanagement system 130 account. An example stored value account comprisesa prepaid account maintained by the payment management system 130. In anexample embodiment, the user 101 designates the stored value account asa preferred account to deduct any payment requests for purchasetransaction from. In an example embodiment, the user 101 is prompted orotherwise notified to “top off” or add funds when the stored valueaccount reaches a designated value. In an example embodiment, the storedvalue account may be funded by any credit account, debit account, bankaccount, or financial account. In another example embodiment, funds maybe added to the stored value account using a pay by electronic mailtransaction, gift card, or offer redemption transaction.

If the transaction is not approved, the method 300 proceeds to block355. In block 355, the transaction is declined and the paymentmanagement system 130 transmits a notice of the declined transaction tothe merchant system 110.

Returning to block 350, if the transaction is approved, the method 300proceeds to block 360. In block 360, the payment management system 130transmits a payment authorization message to the merchant system 110. Inan example embodiment, the payment authorization message is transmittedcomprises an authorization for the amount in the payment request lessthe value of any offers applied. In an example embodiment, the paymentauthorization is processed in a manner consistent with a typical debitcard or credit card transaction. The method for method for transmittingthe payment authorization to the merchant system 110 for the frontingtransaction is described in more detail hereinafter with reference tothe methods described in FIG. 7.

FIG. 7 is a block flow diagram depicting a method 360 for transmittingthe payment authorization to the merchant system 110 for the frontingtransaction, in accordance with certain example embodiments, asreferenced in block 360. The method 360 is described with reference tothe components illustrated in FIGS. 1 and 2.

In block 705, the payment management system 130 updates the dynamicelectronic receipt to reflect approval of the purchase request.Continuing with the previous example as illustrated in FIG. 19, thetransaction is approved for the adjusted purchase request amount of $90($100 less the $10 offer) and the dynamic electronic receipt 3010 wasupdated to reflect the approved transaction.

Returning to FIG. 7, in block 710, the payment management system 130transmits the payment authorization to the card network 140. In anexample embodiment, the payment authorization corresponds to the paymentrequest and is routed to the merchant system 110.

In block 720, the card network 140 receives the payment authorization.

In block 730, the card network 140 transmits the payment authorizationto the acquirer system 150. In an example embodiment, the paymentauthorization comprises an identifier that allows the card network 140to route the payment request the acquirer system 150.

In block 740, the acquirer system 150 receives the paymentauthorization.

In block 750, the acquirer system 150 transmits the paymentauthorization to the merchant system 110. In an example embodiment, thepayment authorization comprises an identifier that allows the acquirersystem 150 to route the payment authorization to the merchant system110.

In block 760, the merchant system 110 receives the paymentauthorization.

In block 770, the merchant system 110 completes the purchase transactionwith the user 101. In an example embodiment, this completes the fronttransaction, as depicted on FIG. 2.

Returning to FIG. 7, from block 770, the method 360 proceeds to block370 in FIG. 3.

Returning to FIG. 3, in block 370 the payment management system 130determines a funding account for the purchase transaction. In an exampleembodiment, this signifies the beginning of the funding transaction, asdepicted on FIG. 2. In an example embodiment, a window of time haspassed between the completion of the fronting transaction, as previouslydescribed, and the funding transaction (for example, 1 minute, 10minutes, 1 hour, 2 days, or another defined period of time). The methodfor determining the funding account for the funding transaction isdescribed in more detail hereinafter with reference to the methodsdescribed in FIG. 8.

FIG. 8 is a block flow diagram depicting a method 370 for determiningthe funding account for the funding transaction, in accordance withcertain example embodiments, as referenced in block 370. The method 370is described with reference to the components illustrated in FIGS. 1 and2.

In block 810, the payment management system 130 identifies the user's101 payment management system 130 account. In an example embodiment, thepayment management system 130 reviews a log of approved transactions andidentifies the user's payment management system 130 account from thelist of approved transactions (for example, the log comprises a list ofapproved transaction for which a funding transaction has not beencompleted).

In block 820, the payment management system 130 determines whether thereis a remaining balance for the funding transaction. In an exampleembodiment, the payment management system subtracts the amount deductedfrom the stored value account from the adjusted transaction amount. Ifthe difference is not equal to zero, the payment management system 130determines that a remaining balance exists for the funding transaction.

If a remaining balance does not exist for the funding transaction, themethod 370 proceeds to block 1170 in FIG. 11.

Returning to block 820, if a remaining balance does exist for thefunding transaction, the method 370 proceeds to block 830.

In block 830, the payment management system 130 identifies the user's101 funding account(s) available. In an example embodiment, the fundingaccounts have been previously designated by the user 101 when creatingor updating the user's payment management system 130 account. In anexample embodiment, the funding accounts are the one or more registeredfinancial accounts previously described with reference to FIG. 3.

In block 840, the payment management system 130 determines whether theuser 101 has additional funding accounts. In an example embodiment, thepayment management system 130 determines whether the user 101 has one ormore funding accounts in addition to the stored value account.

If the user 101 does not have additional funding accounts, the method370 proceeds to block 845.

In block 845, the payment management system 130 overdrafts the user's101 stored value account for the balance of the purchase transaction. Inan example user's stored value account. The user 101 is notified of theoverdraft status of the account and provided an opportunity to add fundsto the stored value account.

Returning to block 840, if the user has additional funding accounts, themethod 370 proceeds to block 850.

In block 850, the payment management system 130 determines whether theuser 101 has identified multiple preferred funding accounts. In anexample embodiment, the user 101 can designate one or more accounts as“preferred” funding accounts. In this embodiment, the payment managementsystem 130 will select the one or more preferred funding accounts tofinance the funding transaction. In an example embodiment, the user 101can designate a preferred funding account when creating the paymentmanagement system 130 account or at any time prior to the beginning ofthe funding transaction. In another example embodiment, the user 101designates one or more rules for selecting the preferred funding account(for example, select account B for a transaction with Merchant X). Inyet another example embodiment, the payment management system 130determines the funding account.

If the user 101 does not have multiple preferred funding accounts, themethod 370 proceeds to block 860. In block 860, the payment managementsystem 130 creates a single payment request for the adjusted paymentamount. In an example embodiment, the adjusted payment amount is theamount from the payment request for the fronting transaction less anoffers applied and less any amount paid from another account (forexample, the stored value account).

From block 860, the method 370 proceeds to block 880.

Returning to block 850, if the user 101 has multiple preferred fundingaccounts, the method 370 proceeds to block 870. In block 870, thepayment management system 130 creates multiple payment requests for theadjusted payment amount. In an example embodiment, the adjusted paymentamount is the amount from the payment request for the frontingtransaction less an offers applied and less any amount paid from anotheraccount (for example, the stored value account). In an exampleembodiment, the user 101 defines rules for determining the amount orpercentage that will be charged to each funding account (for example,change 25% to preferred account A and the remainder to preferred accountB). In another example embodiment, the payment management system 130determines the amount that will be charged to each account (for example,$50 on a gift card with a $50 balance and the remainder on preferredaccount B).

In block 880, the payment management system 130 updates the dynamicelectronic receipt to reflect the payment request(s). Continuing withthe previous example as illustrated in FIG. 20, a payment request for$20 was submitted to the issuer system 160 of Account A, a paymentrequest for $20 was submitted to the issuer system 160 of Account B andthe dynamic electronic receipt 3010 was updated to reflect the paymentrequests.

Returning to FIG. 8, from block 880 the method 370 proceeds to block 380in FIG. 3.

Returning to FIG. 3, in block 380 the payment management system 130transmits the payment request for the funding transaction. In an exampleembodiment, the payment request functions to seek approval for thefunding transaction via the user's 101 financial account. In an exampleembodiment, the payment management system 130 processes the fundingtransaction in a manner consistent with a typical debit card or creditcard transaction. The method for transmitting the payment authorizationrequest for the funding transaction is described in more detailhereinafter with reference to the methods described in FIG. 9.

FIG. 9 is a block flow diagram depicting a method 380 for transmittingthe payment authorization request for the funding transaction, inaccordance with certain example embodiments, as referenced in block 380.The method 380 is described with reference to the components illustratedin FIGS. 1 and 2.

In block 910, the payment management system 130 transmits the paymentrequest to the acquirer system 150.

In block 920, the acquirer system 150 receives the payment request. Inan example embodiment, the acquirer system 150 receives the paymentrequest in a manner consistent with a typical debit card or credit cardtransaction.

In block 930, the acquirer system 150 transmits the payment request to acard network 140. In an example embodiment, the acquirer system 150transmits the payment request in a manner consistent with a typicaldebit card or credit card transaction.

In block 940, the card network 140 receives the payment request. In anexample embodiment, the card network 140 receives the payment request ina manner consistent with a typical debit card or credit cardtransaction.

In block 950, the card network 140 transmits the payment request to theissuer system 160 that corresponds to the user's selected financialaccount. In an example embodiment, the account information can be readand understood by the card network 140, which allows the card network140 to transmit the request to the issuer system 160. In thisembodiment, the card network 140 reads an account number from theaccount information and determines, based on a series of numbers orrouting information contained in the account number, that the paymentrequest should be transmitted to the issuer system 160.

In block 960, the issuer system 160 receives the payment request.

In an example embodiment, the methods described in FIG. 9 are repeatedfor each funding account selected in block 890 of FIG. 8, if applicable.

The method 380 then proceeds to block 385 in FIG. 3.

Returning to FIG. 3, in block 385 the issuer system 160 approves ordeclines the transaction. In an example embodiment, the issuer system160 determines if the user 101 has a sufficient available balance forthe transaction.

If the transaction is not approved, the method 300 proceeds to block390. In block 390, the payment management system 130 receivesnotification of the declined transaction. The method for transmitting apayment declination notification for the funding transaction, isdescribed in more detail hereinafter with reference to the methodsdescribed in FIG. 10.

FIG. 10 is a block flow diagram depicting a method 390 for transmittingthe payment declination notification for the funding transaction, inaccordance with certain example embodiments, as referenced in block 390.The method 390 is described with reference to the components illustratedin FIGS. 1 and 2.

In block 1010, the issuer system 160 transmits the declination notice tothe card network 140. In an example embodiment, the declination noticecorresponds to the payment request and is routed to the paymentmanagement system 130.

In block 1020, the card network 140 receives the declination notice.

In block 1030, the card network 140 transmits the declination notice tothe acquirer system 150. In an example embodiment, the declinationnotice comprises an identifier that allows the card network 140 to routethe declination notice the acquirer system 150.

In block 1040, the acquirer system 150 receives the declination notice.

In block 1050, the acquirer system 150 transmits the declination noticeto the payment management system 130. In an example embodiment, thedeclination notice comprises an identifier that allows the acquirersystem 140 to route the declination notice to the payment managementsystem 130.

In block 1060, the payment management system 130 receives thedeclination notice.

In block 1070, the payment management system 130 updates the dynamicelectronic receipt to reflect the payment declination for the fundingtransaction. Continuing with the previous example as illustrated in FIG.21, a declination notice that corresponds to the $20 payment requestsubmitted to the issuer system 160 of Account A and the dynamicelectronic receipt 3010 was updated to reflect the declination notice.

Returning to FIG. 10, from block 1070 the method 390 proceeds to block370 in FIG. 3. In an example embodiment, the methods described in block370 through 385 are repeated until the balance of the frontingtransaction is paid (for example, until a payment authorization isreceived for the remaining balance or until the stored value account isoverdraft for the remaining balance).

Returning to block 385 of FIG. 3, if the transaction is approved, themethod 300 then proceeds to block 395. In block 395, the paymentmanagement system 130 receives a payment authorization for the fundingtransaction. The method for transmitting the payment authorizationnotification for the funding transaction is described in more detailhereinafter with reference to the methods described in FIG. 11.

FIG. 11 is a block flow diagram depicting a method 395 for transmittingthe payment authorization notification for the funding transaction, inaccordance with certain example embodiments, as referenced in block 395.The method 395 is described with reference to the components illustratedin FIGS. 1 and 2.

In block 1110, the issuer system 160 transmits the payment authorizationto the card network 140. In an example embodiment, the paymentauthorization corresponds to the payment request and is routed to thepayment management system 130.

In block 1120, the card network 140 receives the payment authorization.

In block 1130, the card network 140 transmits the payment authorizationto the acquirer system 150. In an example embodiment, the paymentauthorization comprises an identifier that allows the card network 140to route the payment authorization the acquirer system 150.

In block 1140, the acquirer system 150 receives the paymentauthorization.

In block 1150, the acquirer system 150 transmits the paymentauthorization to the payment management system 130. In an exampleembodiment, the payment authorization comprises an identifier thatallows the acquirer system 140 to route the payment authorization to thepayment management system 130.

In block 1160, the payment management system 130 receives the paymentauthorization.

In block 1170, the payment management system 130 updates the dynamicelectronic receipt to reflect the payment authorization for the fundingtransaction. Continuing with the previous example as illustrated in FIG.22, a payment authorization that corresponds to the $20 payment requestsubmitted to the issuer system 160 of Account B and the dynamicelectronic receipt 3010 was updated to reflect the paymentauthorization. In addition, a payment request for $20 was submitted tothe issuer system 160 of Account C, a corresponding paymentauthorization was received, and the dynamic electronic receipt 3010 wasupdated to reflect the payment request and payment authorization.

FIG. 12 is a block flow diagram depicting a method for processing areturn transaction, in accordance with certain example embodiments. Themethod 1200 is described with reference to the components illustrated inFIGS. 1 and 2.

In block 1210, the user 101 initiates a return transaction with themerchant. In an example embodiment, the user 101 initiates a returntransaction by taking a product back to a retail location or sending aproduct back to an online marketplace and presenting the user's 101payment management system 130 account identifier.

In an example embodiment, the merchant system 110 operates an onlinemarketplace and the user 101 enters the account identifier at thereturns webpage or other suitable location. The merchant system 110online marketplace provides a link, button, or other control that allowsthe user 101 to automatically transmit the user's payment managementsystem 130 account information to the merchant system 110). In thisembodiment, the user 101 is prompted to log into, has previously logged,or is otherwise automatically logged into the payment management system130. In another example embodiment, the user's 101 login credentials areshared across other accounts (for example, social networking websitesand user device 120 accounts) and the user 101 is automatically loggedinto the payment management system 140 account using the shared logincredentials.

In another example embodiment, the merchant system 110 operates a retailstore. In this embodiment, the user 101 may use the user account device105 in a manner consistent with a magnetic stripe credit card. Inanother embodiment, a payment code is displayed on the user interface121 of the user device 120 in a manner that the merchant system 110and/or user 101 can read the code. In an example embodiment, the paymentcode is a bar code, QR code, or other machine-readable code that iscapable of being scanned by a code scanner or otherwise readable by themerchant system 110. In another example embodiment, the payment code isdisplayed on the user interface 121 so that a merchant operating themerchant system 110 can read and physically enter the payment code intothe POS terminal 115. In an alternative example embodiment, the paymentcode is read by the user 101 and entered into the POS terminal 115.

In another example embodiment, the user 101 using the user device 120 toinitiate a contactless “tap” with the POS terminal 115. In operation ofan NFC, Bluetooth, Wi-Fi, or other wireless transaction, the user 101“taps” the user device 120, such as an NFC-enabled user device 120, toPOS terminal 115 of a point of sale system. The POS terminal 115recognizes the NFC-enabled device 120 when the device is moved withinrange of the POS terminal 115, establishes a secure communicationchannel with the device 120, and initiates a refund transaction betweenthe POS terminal 115 and the device 120.

In block 1220, the merchant system 110 transmits a refund request forthe return transaction to the account management system 130. In anexample embodiment, the submission of the refund request by the merchantsystem 110 for the purchase transaction signifies the beginning of thefronting transaction as illustrated on FIG. 2. The refund requestfunctions to seek approval for the return transaction via the accountinformation provided by the user 101. In an example embodiment, themerchant system 110 processes the return transaction in a mannerconsistent with a typical debit card or credit card return transaction.The method for transmitting the return authorization request to thepayment management system 130 for the fronting transaction is describedin more detail hereinafter with reference to the methods described inFIG. 13.

FIG. 13 is a block flow diagram depicting a method 1200 for transmittingthe refund notification to the payment management system 130, inaccordance with certain example embodiments, as referenced in block1220. The method 1220 is described with reference to the componentsillustrated in FIGS. 1 and 2.

In block 1310, the merchant system 110 generates a refund requestmessage to request a refund using the account information provided bythe user 101 in block 1210 and transmits the refund request to anacquirer system 150. In an example embodiment, the account informationresembles actual debit/credit card information and the POS terminal 115processes the transaction in a manner consistent with a typical refundrequest.

In block 1320, the acquirer system 150 receives the refund request. Inan example embodiment, the acquirer system 150 receives the refundrequest in a manner consistent with a typical debit card or credit cardrefund transaction.

In block 1330, the acquirer system 150 transmits the refund request to acard network 140. In an example embodiment, the acquirer system 150transmits the refund request in a manner consistent with a typical debitcard or credit card refund transaction. In an example embodiment, theaccount information provided by the user 101 in block 1210 can be readand understood by the acquirer system 150, which allows the acquirersystem 150 to transmit the request to the appropriate card network 140.

In block 1340, the card network receives the refund request. In anexample embodiment, the card network receives the refund request in amanner consistent with a typical debit card or credit card refundtransaction.

In block 1350, the card network 140 transmits the refund request to thepayment management system 130. In an example embodiment, the accountinformation provided by the user 101 in block 1210 can be read andunderstood by the card network 140, which allows the card network 140 totransmit the request to the payment management system 130. In thisembodiment, the card network 140 reads an account number from theaccount information and determines, based on a series of numbers orrouting information contained in the account number, that the refundrequest should be transmitted to the payment management system 130.

In block 1360, the payment management system 130 receives the refundrequest.

The method 1310 then proceeds to block 1230 in FIG. 12.

Returning to FIG. 12, in block 1230, the payment management system 130identifies the user 101 account associated with the refund requestreceived from the merchant system 110. In an example embodiment, thepayment management system 130 uses the information contained in therefund request to identify the user's 101 account. In an exampleembodiment, the payment management system 130 reads the user's 101account identification information from the refund request. In anexample embodiment, the user's 101 identification information iscontained in or encoded by the account information. In another exampleembodiment, the payment management system 130 cross-references a list ofgenerated account numbers to determine the corresponding user 101account.

In another example embodiment, the user 101 is conducting an onlinereturn transaction with the merchant system 110 or a transaction via amerchant shopping application 123 resident on the user device 120 andthe user 101 is logged into the user's payment management system 130account.

In block 1240, the payment management system 130 reads the user's 101approved transaction for the previous three months. In an exampleembodiment, a log of the user's approved transactions is maintained inthe user's 101 payment management system 130 account such that thesystem 130 can retrieve and review a list of the previous transactionswhen processing the return. In another example embodiment, the paymentmanagement system retrieves and reviews the dynamic electronic receiptsmaintained in the user's payment management system 130 account to locatethe user's previous transactions when processing the return.

In block 1250, the payment management system 130 identifies the paymentaccount for the funding transaction that corresponds to the returntransaction. In an example embodiment, the payment management system 130funds the return transaction to the same account or accounts in whichthe original payment transaction was funded by. In this example, thereturn transaction is applied to the funding accounts in reverse orderto that in which the funding transaction was applied. For example,continuing with the previous example described with reference to FIG.22, the payment management system 130 would fund $20 of the refund toAccount C, then $20 to Account B, and finally $50 to the Stored ValueAccount. The method for identifying the payment account for the fundingtransaction that corresponds to the return transaction is described inmore detail hereinafter with reference to the methods described in FIG.14.

FIG. 14 is a block flow diagram depicting a method 1250 for identifyingthe payment account for the funding transaction that corresponds to thereturn transaction, in accordance with certain example embodiments, asreferenced in block 1250. The method 1250 is described with reference tothe components illustrated in FIGS. 1 and 2.

In block 1410, the payment management system 130 compares the returnamount of the refund request to the approved transaction amount for theidentified transactions for the previous three months. In an exampleembodiment, the payment management system 130 reviews the transactionapproval amount designated for each funding transaction and comparesthat amount to the refund amount on the refund request.

In block 1420, the payment management system 130 determines whether therefund amount is less than or equal to the transaction approval amountdesignated for each of the identified funding transactions. In anexample embodiment, a refund transaction is for an item or portion ofthe purchase transaction. In this embodiment, the amount of the refundrequest is less than the transaction approval amount designated for thefunding transaction.

In another example embodiment, the refund transaction is for the entirepurchase transaction. In this embodiment, the amount of the refund isequal to the transaction approval amount designated for the fundingtransaction. In an example embodiment, the payment management system 130compares these amounts to make the determination.

If the refund amount is not less than or equal to the transactionapproval amount designated for any of the identified fundingtransactions, the method 1350 proceeds to block 1270 in FIG. 12.

Returning to block 1420, if the refund amount is less than or equal tothe transaction approval amount designated for any of the identifiedfunding transactions, the method 1350 proceeds to block 1430.

In block 1430, the payment management system 130 compares the merchantidentification (ID) code for the approved transaction to the merchant IDcode on the refund request. In an example embodiment, the paymentmanagement system 130 reads the merchant ID code from the refund requestand cross-references the code to the merchant ID codes of known merchantsystems to identify the merchant system 110. In an example embodiment,the merchant system 110 has previously provided the payment managementsystem 130 with a merchant's ID code (for example, when registering withthe payment management system 130, when providing the payment managementsystem 130 offers for distribution, or when otherwise conductingbusiness with the payment management system 130).

In another example embodiment, the refund request does not contain themerchant ID and the payment management system 130 reads a merchantdescriptor from the refund request. In an example embodiment, thepayment request comprises the merchant ID code and/or a descriptor thatidentifies the merchant system 110. The merchant descriptor comprises aname or other descriptor that identifies the merchant system 110. In anexample embodiment, the descriptor can comprise an identification of abranch, franchise, or division of a merchant system (for example, a fastfood restaurant franchise located on street X in town Z). The paymentmanagement system 130 identifies the merchant system 110 based on themerchant descriptor read from the refund request.

In block 1440, the payment management system 130 determines whether themerchant ID code from the refund request corresponds to the merchant IDcode from the identified transactions. In an example embodiment, themerchant ID code is available and the payment management system 130compares the merchant ID code provided in the payment request to themerchant ID code for the identified purchase transactions. In anotherexample embodiment, the payment management system 130 compares themerchant descriptor to the merchant descriptor and/or merchant IDprovided in the identified purchase transactions.

If the merchant ID codes do not match, the method 1350 proceeds to block1280 in FIG. 12.

Returning to block 1440, if the merchant ID codes do match, the method1350 proceeds to block 1450. In block 1450, the payment managementsystem comparers the merchant category codes (MCC) on the refund requestto the MCC on the identified transactions. In an example embodiment, theMCC classifies the merchant system 110 by the type of goods and/orservices provided. This allows the issuer system 160 to provide rewardsbased on types of purchases, provide users 101 with feedback regardingthe types of goods/services purchased, or to provide a spendinganalysis. In an example embodiment, the MCC are provided on the frontingtransaction purchase request and are recorded on the dynamic electronicreceipt and/or another record of the transaction.

In block 1460, the payment management system 130 determines whether theMCC from the refund request matches the MCC from the identifiedtransactions. In an example embodiment, the payment management systemcross-references the codes to determine if they match.

If the codes do not match, the method 1350 proceeds to block 1270 inFIG. 12.

Returning to block 1460, if the MCC match, the method 1350 proceeds toblock 1280 in FIG. 12.

In an example embodiment, the methods described in FIG. 14 can beperformed in any order. For example, the payment management system 130may compare the transaction amounts pursuant to the methods described inblocks 1410-1420 and then compare the MCC pursuant to the methodsdescribed in block 1450-1460.

In another example embodiment, the payment management system 130 mayemploy any other form of logic to determine the original fundingaccount. For example, if the user 101 has only a single funding account,the payment management system 130 will identify that account, or if theuser 101 has only performed a single transaction, the payment managementsystem 130 will identify that account.

The method 1350 then proceeds to block 1260 in FIG. 12.

In block 1260, the payment management system 130 determines whether thepayment account corresponding the original funding transaction wasidentified and identifies the issuer system 160 that corresponds to thatpayment account. In an example embodiment, the corresponding paymentaccount is identified pursuant to the methods described with referenceto FIG. 13.

If the corresponding payment account and issuer system 160 were notidentified, the method 1200 proceeds to block 1270. In block 1270, thepayment management system 130 refunds the refund transaction amount tothe user's 101 stored value account. In an example embodiment, thepayment management system 130 is the issuer system 160 that maintainsthe user's 101 stored value account. In another example embodiment, athird party system maintains the user's 101 stored value account and thepayment management system 130 submits a refund notification to theissuer system 160 of the stored value account pursuant to the methodsdescribed with reference to block 1280 in FIG. 12.

Returning to block 1260, if the corresponding payment account and issuersystem 160 were identified, the method 1200 proceeds to block 1280. Inblock 1280, the payment management system 130 submits a refundnotification to the issuer system(s) 160 of the identified fundingaccount. The method for transmitting the refund notification to theissuer system 160 of the payment account for the funding transactionthat corresponds to the return transaction is described in more detailhereinafter with reference to the methods described in FIG. 15.

FIG. 15 is a block flow diagram depicting a method 1280 for transmittingthe refund notification to the issuer system 160 of the payment accountfor the funding transaction that corresponds to the return transaction,in accordance with certain example embodiments, as referenced in block1280. The method 1280 is described with reference to the componentsillustrated in FIGS. 1 and 2.

In block 1510, the payment management system 130 transmits the refundrequest to the acquirer system 150.

In block 1520, the acquirer system 150 receives the refund request. Inan example embodiment, the acquirer system 150 receives the refundrequest in a manner consistent with a typical debit card or credit cardrefund transaction.

In block 1530, the acquirer system 150 transmits the refund request to acard network 140. In an example embodiment, the acquirer system 150transmits the refund request in a manner consistent with a typical debitcard or credit card refund transaction.

In block 1540, the card network 140 receives the refund request. In anexample embodiment, the card network 140 receives the refund request ina manner consistent with a typical debit card or credit card refundtransaction.

In block 1540, the card network 140 transmits the refund request to theissuer system 160 that corresponds to the user's selected financialaccount. In an example embodiment, the account information can be readand understood by the card network 140, which allows the card network140 to transmit the request to the issuer system 160. In thisembodiment, the card network 140 reads an account number from theaccount information and determines, based on a series of numbers orrouting information contained in the account number, that the refundrequest should be transmitted to the issuer system 160.

In block 1560, the issuer system 160 receives the refund request.

In an example embodiment, the methods described in FIG. 15 are repeatedfor each funding account identified in block 1260 of FIG. 12, ifapplicable.

The method 1280 then proceeds to block 1290 in FIG. 12.

Returning to FIG. 12, in block 1290, the payment management systemupdates the dynamic electronic receipt to reflect the refund. Continuingwith the previous example as illustrated in FIG. 23, a refund requestthat corresponds to the $20 payment request was submitted to the issuersystem 160 of Account C and the dynamic electronic receipt 3010 wasupdated to reflect the refund request. In addition, a refund request for$20 was submitted to the issuer system 160 of Account B and the dynamicelectronic receipt 3010 was updated to reflect the refund request.Finally, a refund to the user's 101 Stored Value Account for $50 wasprocessed and the dynamic electronic receipt 3010 was updated to reflectthe refund.

Other Example Embodiments

FIG. 16 depicts a computing machine 2000 and a module 2050 in accordancewith certain example embodiments. The computing machine 2000 maycorrespond to any of the various computers, servers, mobile devices,embedded systems, or computing systems presented herein. The module 2050may comprise one or more hardware or software elements configured tofacilitate the computing machine 2000 in performing the various methodsand processing functions presented herein. The computing machine 2000may include various internal or attached components such as a processor2010, system bus 2020, system memory 2030, storage media 2040,input/output interface 2060, and a network interface 2070 forcommunicating with a network 2080.

The computing machine 2000 may be implemented as a conventional computersystem, an embedded controller, a laptop, a server, a mobile device, asmartphone, a set-top box, a kiosk, a vehicular information system, onemore processors associated with a television, a customized machine, anyother hardware platform, or any combination or multiplicity thereof. Thecomputing machine 2000 may be a distributed system configured tofunction using multiple computing machines interconnected via a datanetwork or bus system.

The processor 2010 may be configured to execute code or instructions toperform the operations and functionality described herein, managerequest flow and address mappings, and to perform calculations andgenerate commands. The processor 2010 may be configured to monitor andcontrol the operation of the components in the computing machine 2000.The processor 2010 may be a general purpose processor, a processor core,a multiprocessor, a reconfigurable processor, a microcontroller, adigital signal processor (DSP), an application specific integratedcircuit (ASIC), a graphics processing unit (GPU), a field programmablegate array (FPGA), a programmable logic device (PLD), a controller, astate machine, gated logic, discrete hardware components, any otherprocessing unit, or any combination or multiplicity thereof. Theprocessor 2010 may be a single processing unit, multiple processingunits, a single processing core, multiple processing cores, specialpurpose processing cores, co-processors, or any combination thereof.According to certain embodiments, the processor 2010 along with othercomponents of the computing machine 2000 may be a virtualized computingmachine executing within one or more other computing machines.

The system memory 2030 may include non-volatile memories such asread-only memory (ROM), programmable read-only memory (PROM), erasableprogrammable read-only memory (EPROM), flash memory, or any other devicecapable of storing program instructions or data with or without appliedpower. The system memory 2030 may also include volatile memories such asrandom access memory (RAM), static random access memory (SRAM), dynamicrandom access memory (DRAM), and synchronous dynamic random accessmemory (SDRAM). Other types of RAM also may be used to implement thesystem memory 2030. The system memory 2030 may be implemented using asingle memory module or multiple memory modules. While the system memory2030 is depicted as being part of the computing machine 2000, oneskilled in the art will recognize that the system memory 2030 may beseparate from the computing machine 2000 without departing from thescope of the subject technology. It should also be appreciated that thesystem memory 2030 may include, or operate in conjunction with, anon-volatile storage device such as the storage media 2040.

The storage media 2040 may include a hard disk, a floppy disk, a compactdisc read only memory (CD-ROM), a digital versatile disc (DVD), aBlu-ray disc, a magnetic tape, a flash memory, other non-volatile memorydevice, a solid state drive (SSD), any magnetic storage device, anyoptical storage device, any electrical storage device, any semiconductorstorage device, any physical-based storage device, any other datastorage device, or any combination or multiplicity thereof. The storagemedia 2040 may store one or more operating systems, application programsand program modules such as module 2050, data, or any other information.The storage media 2040 may be part of, or connected to, the computingmachine 2000. The storage media 2040 may also be part of one or moreother computing machines that are in communication with the computingmachine 2000 such as servers, database servers, cloud storage, networkattached storage, and so forth.

The module 2050 may comprise one or more hardware or software elementsconfigured to facilitate the computing machine 2000 with performing thevarious methods and processing functions presented herein. The module2050 may include one or more sequences of instructions stored assoftware or firmware in association with the system memory 2030, thestorage media 2040, or both. The storage media 2040 may thereforerepresent examples of machine or computer readable media on whichinstructions or code may be stored for execution by the processor 2010.Machine or computer readable media may generally refer to any medium ormedia used to provide instructions to the processor 2010. Such machineor computer readable media associated with the module 2050 may comprisea computer software product. It should be appreciated that a computersoftware product comprising the module 2050 may also be associated withone or more processes or methods for delivering the module 2050 to thecomputing machine 2000 via the network 2080, any signal-bearing medium,or any other communication or delivery technology. The module 2050 mayalso comprise hardware circuits or information for configuring hardwarecircuits such as microcode or configuration information for an FPGA orother PLD.

The input/output (I/O) interface 2060 may be configured to couple to oneor more external devices, to receive data from the one or more externaldevices, and to send data to the one or more external devices. Suchexternal devices along with the various internal devices may also beknown as peripheral devices. The I/O interface 2060 may include bothelectrical and physical connections for operably coupling the variousperipheral devices to the computing machine 2000 or the processor 2010.The I/O interface 2060 may be configured to communicate data, addresses,and control signals between the peripheral devices, the computingmachine 2000, or the processor 2010. The I/O interface 2060 may beconfigured to implement any standard interface, such as small computersystem interface (SCSI), serial-attached SCSI (SAS), fiber channel,peripheral component interconnect (PCI), PCI express (PCIe), serial bus,parallel bus, advanced technology attached (ATA), serial ATA (SATA),universal serial bus (USB), Thunderbolt, FireWire, various video buses,and the like. The I/O interface 2060 may be configured to implement onlyone interface or bus technology. Alternatively, the I/O interface 2060may be configured to implement multiple interfaces or bus technologies.The I/O interface 2060 may be configured as part of, all of, or tooperate in conjunction with, the system bus 2020. The I/O interface 2060may include one or more buffers for buffering transmissions between oneor more external devices, internal devices, the computing machine 2000,or the processor 2010.

The I/O interface 2060 may couple the computing machine 2000 to variousinput devices including mice, touch-screens, scanners, electronicdigitizers, sensors, receivers, touchpads, trackballs, cameras,microphones, keyboards, any other pointing devices, or any combinationsthereof. The I/O interface 2060 may couple the computing machine 2000 tovarious output devices including video displays, speakers, printers,projectors, tactile feedback devices, automation control, roboticcomponents, actuators, motors, fans, solenoids, valves, pumps,transmitters, signal emitters, lights, and so forth.

The computing machine 2000 may operate in a networked environment usinglogical connections through the network interface 2070 to one or moreother systems or computing machines across the network 2080. The network2080 may include wide area networks (WAN), local area networks (LAN),intranets, the Internet, wireless access networks, wired networks,mobile networks, telephone networks, optical networks, or combinationsthereof. The network 2080 may be packet switched, circuit switched, ofany topology, and may use any communication protocol. Communicationlinks within the network 2080 may involve various digital or an analogcommunication media such as fiber optic cables, free-space optics,waveguides, electrical conductors, wireless links, antennas,radio-frequency communications, and so forth.

The processor 2010 may be connected to the other elements of thecomputing machine 2000 or the various peripherals discussed hereinthrough the system bus 2020. It should be appreciated that the systembus 2020 may be within the processor 2010, outside the processor 2010,or both. According to some embodiments, any of the processor 2010, theother elements of the computing machine 2000, or the various peripheralsdiscussed herein may be integrated into a single device such as a systemon chip (SOC), system on package (SOP), or ASIC device.

In situations in which the systems discussed here collect personalinformation about users, or may make use of personal information, theusers may be provided with an opportunity or option to control whetherprograms or features collect user information (e.g., information about auser's social network, social actions or activities, profession, auser's preferences, or a user's current location), or to control whetherand/or how to receive content from the content server that may be morerelevant to the user. In addition, certain data may be treated in one ormore ways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over how information is collected about the userand used by a content server.

Embodiments may comprise a computer program that embodies the functionsdescribed and illustrated herein, wherein the computer program isimplemented in a computer system that comprises instructions stored in amachine-readable medium and a processor that executes the instructions.However, it should be apparent that there could be many different waysof implementing embodiments in computer programming, and the embodimentsshould not be construed as limited to any one set of computer programinstructions. Further, a skilled programmer would be able to write sucha computer program to implement an embodiment of the disclosedembodiments based on the appended flow charts and associated descriptionin the application text. Therefore, disclosure of a particular set ofprogram code instructions is not considered necessary for an adequateunderstanding of how to make and use embodiments. Further, those skilledin the art will appreciate that one or more aspects of embodimentsdescribed herein may be performed by hardware, software, or acombination thereof, as may be embodied in one or more computingsystems. Moreover, any reference to an act being performed by a computershould not be construed as being performed by a single computer as morethan one computer may perform the act.

The example embodiments described herein can be used with computerhardware and software that perform the methods and processing functionsdescribed herein. The systems, methods, and procedures described hereincan be embodied in a programmable computer, computer-executablesoftware, or digital circuitry. The software can be stored oncomputer-readable media. For example, computer-readable media caninclude a floppy disk, RAM, ROM, hard disk, removable media, flashmemory, memory stick, optical media, magneto-optical media, CD-ROM, etc.Digital circuitry can include integrated circuits, gate arrays, buildingblock logic, field programmable gate arrays (FPGA), etc.

The example systems, methods, and acts described in the embodimentspresented previously are illustrative, and, in alternative embodiments,certain acts can be performed in a different order, in parallel with oneanother, omitted entirely, and/or combined between different exampleembodiments, and/or certain additional acts can be performed, withoutdeparting from the scope and spirit of various embodiments. Accordingly,such alternative embodiments are included in the invention claimedherein.

Although specific embodiments have been described above in detail, thedescription is merely for purposes of illustration. It should beappreciated, therefore, that many aspects described above are notintended as required or essential elements unless explicitly statedotherwise. Modifications of, and equivalent components or actscorresponding to, the disclosed aspects of the example embodiments, inaddition to those described above, can be made by a person of ordinaryskill in the art, having the benefit of the present disclosure, withoutdeparting from the spirit and scope of embodiments defined in thefollowing claims, the scope of which is to be accorded the broadestinterpretation so as to encompass such modifications and equivalentstructures.

What is claimed is:
 1. A computer-implemented method for applying basketlevel offers during purchase transactions that utilize delayedprocessing windows, comprising: receiving, by one or more computingdevices, a merchant payment request from one or more computing devicesoperated by a merchant system, the merchant payment request comprisingan account identifier for a user account maintained by a paymentmanagement system, a transaction value, and a merchant descriptor, andwherein the merchant payment request seeks authorization for a paymenttransaction between the a user and the merchant system; determining, bythe one or more computing devices, an identity of the merchant systemusing the merchant descriptor; identifying, by the one or more computingdevices, one or more available offers by comparing the identity of themerchant system to known offers; determining, by the one or morecomputing devices, that one or more redemption rules for the one or moreavailable offers are satisfied by the payment transaction between theuser and the merchant system; in response to determining that the one ormore redemption rules are satisfied, redeeming, by the one or morecomputing devices, the one of more offers by adjusting the transactionvalue by an amount of the one or more offers; determining, by the one ormore computing devices, to approve the merchant payment request for theadjusted transaction value prior to requesting a funding payment requestfrom an issuer of one or more financial accounts saved in the useraccount maintained by the payment management system; in response todetermining to approve the merchant payment request, transmitting, bythe one or more computing device, a merchant payment authorization tothe one or more computing devices operated by the merchant system forthe adjusted transaction value; and submitting, by the one or morecomputing devices, a backing payment request, wherein a window of timehas passed between the transmission of the merchant paymentauthorization and the submission of the backing payment request.
 2. Thecomputer-implemented method of claim 1, wherein the offers comprise oneor more of a coupon, loyalty point reward, prepaid offer, and rebate. 3.The computer-implemented method of claim 1, wherein the merchantdescriptor comprises one or more of a merchant identification (ID) code,merchant name, address, phone number, franchise name, franchiselocation, franchisee or owner name, and franchisee or branch number. 4.The computer-implemented method of claim 1, wherein determining theidentity of the merchant system comprises comparing the merchantidentifier to a known merchant system.
 5. The computer-implementedmethod of claim 1, wherein identifying the one or more available offerscomprises cross-referencing the identity of the merchant system with alist of known merchant systems.
 6. The computer-implemented method ofclaim 1, further comprising determining, by the one or more computingdevices, which user account corresponds to the account identifier,wherein the one or more available offers are identified from the useraccount.
 7. The computer-implemented method of claim 1, wherein the oneor more redemption rules comprise an expiration date, a transactionamount minimum, a time limitation, a minimum number of purchasesrequirement, and a location restriction.
 8. The computer-implementedmethod of claim 1, further comprising marking, by the one or morecomputing devices, the one or more redeemed offers as redeemed by theuser.
 9. The computer-implemented method of claim 1, further comprisingdetermining, by the one or more computing devices, which of the one ormore financial accounts saved in the user account maintained by thepayment management system to request the funding payment from bysubmitting the backing payment request.
 10. The computer-implementedmethod of claim 1, further comprising receiving, by the one or morecomputing devices, a payment notification from the issuer of thefinancial account.
 11. A computer program product, comprising: anon-transitory computer-readable medium having computer-readable programinstructions embodied therein that when executed by a computer cause thecomputer for applying basket level offers during purchase transactionsthat utilize delayed processing windows, the computer-readable programinstructions comprising: computer-readable program instructions toreceive a merchant payment request from one or more computing devicesoperated by a merchant system, the merchant payment request comprisingan account identifier for a user account maintained by a paymentmanagement system, a transaction value, and a merchant descriptor, andwherein the merchant payment request seeks authorization for a paymenttransaction between the a user and the merchant system;computer-readable program instructions to determine an identity of themerchant system using the merchant descriptor; computer-readable programinstructions to identify one or more available offers by comparing theidentity of the merchant system to known offers; computer-readableprogram instructions to redeem the one of more offers by adjusting thetransaction value by an amount of the one or more offers;computer-readable program instructions to determine to approve themerchant payment request for the adjusted transaction value prior torequesting a funding payment request from an issuer of one or morefinancial accounts saved in the user account maintained by the paymentmanagement system; computer-readable program instructions to, inresponse to determining to approve the merchant payment request,transmit a merchant payment authorization to the one or more computingdevices operated by the merchant system for the adjusted transactionvalue; and computer-readable program instructions to submit a backingpayment request, wherein a window of time has passed between thetransmission of the merchant payment authorization and the submission ofthe backing payment request.
 12. The computer program product of claim11, wherein the merchant descriptor comprises one or more of a merchantidentification (ID) code, merchant name, address, phone number,franchise name, franchise location, franchisee or owner name, andfranchisee or branch number.
 13. The computer program product of claim11, wherein determining the identity of the merchant system comprisescomparing the merchant identifier to a known merchant system.
 14. Thecomputer program product of claim 11, wherein identifying the one ormore available offers comprises cross-referencing the identity of themerchant system with a list of known merchant systems.
 15. The computerprogram product of claim 11, further comprising computer-readableprogram instructions to determine which user account corresponds to theaccount identifier, wherein the one or more available offers areidentified from the user account.
 16. The computer program product ofclaim 11, further comprising computer-readable program instructions todetermine which of the one or more financial accounts saved in the useraccount maintained by the payment management system to request thefunding payment from by submitting the backing payment request.
 17. Asystem for applying basket level offers during purchase transactionsthat utilize delayed processing windows, the system comprising: astorage medium; and a processor communicatively coupled to the storagemedium, wherein the processor executes application code instructionsthat are stored in the storage medium and that cause the system to:receive a merchant payment request from one or more computing devicesoperated by a merchant system, the merchant payment request comprisingan account identifier for a user account maintained by a paymentmanagement system, a transaction value, and a merchant descriptor, andwherein the merchant payment request seeks authorization for a paymenttransaction between the a user and the merchant system; identify one ormore available offers using the merchant descriptor; redeem the one ofmore offers by adjusting the transaction value by an amount of the oneor more offers; determine to approve the merchant payment request forthe adjusted transaction value prior to requesting a funding paymentrequest from an issuer of one or more financial accounts saved in theuser account maintained by the payment management system; in response todetermining to approve the merchant payment request, transmit a merchantpayment authorization to the one or more computing devices operated bythe merchant system for the adjusted transaction value; and submit abacking payment request, wherein a window of time has passed between thetransmission of the merchant payment authorization and the submission ofthe backing payment request.
 18. The system of claim 17, wherein theprocessor is further configured to execute computer-executableinstructions stored in the storage medium to cause the system toidentify the merchant system using the merchant descriptor.
 19. Thesystem of claim 18, wherein determining the identity of the merchantsystem comprises comparing the merchant identifier to a known merchantsystem.
 20. The system of claim 17, further comprising computer-readableprogram instructions to determine which user account corresponds to theaccount identifier, wherein the one or more available offers areidentified from the user account.